Systems and methods for optimizing message notification based on geographic location and time

ABSTRACT

Systems and methods are provided for optimizing delivery of messages to mobile device users, the method comprising receiving a message to be sent to a client application executable at a mobile device of a user, along with an associated time constraint and an associated geographic constraint; determining a current time at the mobile device and a current geographic location of the mobile device via a communication network; determining, upon receiving the current geographic location of the mobile device and the current time of the mobile device, whether the current geographic location of the mobile device complies with the associated geographic constraint for the message to be sent to the client application and determining whether the current time of the mobile device complies with the associated time constraint for the message to be sent to the client application; and sending, when the current geographic location of the mobile device is determined to comply with the associated geographic constraint and when the current time of the mobile device is determined to comply with the associated time constraint, the message for display to the user at the mobile device via a message notification interface of an operating system of the mobile device.

TECHNICAL FIELD

The present disclosure relates generally to location- and time-basedservices for mobile device users and, more particularly, to providingmessaging services to particular mobile device users based on theirrespective geographic locations and/or a time constraint.

BACKGROUND

Mobile devices, such as smartphones, now allow users to perform avariety of tasks that traditionally required different types of devices.For example, a user may be able to use different client applicationsexecutable at the same mobile device to browse online content, playaudio files, capture digital images, view directions for navigatingbetween different locations or points of interest, and exchange messagesbetween other users or computing devices via a mobile communicationnetwork. A user may also download and install various third-party clientapplications at the user's mobile device for receiving messages, viewinginformation, and viewing content related to general topics of interest.An application developer or affiliated service provider may use such aclient application to provide different services to the user. Suchservices may include messaging services through which users maycorrespond with themselves or each other through messages. Othermessaging services may include subscription services in order toreceive, for example, real-time message notifications or breaking newsalerts at the user's mobile device. The message notifications or alertsthat are sent (or “pushed”) by a service provider for a particularclient application may be displayed within a general notificationswindow via a user interface of the operating system at the user's mobiledevice, even though the client application may be closed or not beactively executing at the mobile device when such notifications arereceived.

Conventional solutions for delivering messages to a user's mobile devicetypically do not take into account the current location of the mobiledevice or the current time. Hence, the messages to the user's mobiledevice usually are delivered immediately when sent without regard to aparticular time and/or to the user's current geographic location.Moreover, conventional solutions may not provide a way to delivermessages that are relevant to the user's current location at anappropriate time.

SUMMARY OF THE DISCLOSURE

Embodiments disclose systems and methods for timing messagenotifications so as to optimize the delivery of targeted content tomobile device users.

According to certain embodiments, methods are disclosed for optimizingdelivery of messages to mobile device users. The method includesreceiving a message to be sent to a client application executable at amobile device of a user, along with an associated time constraint and anassociated geographic constraint, and determining a current time at themobile device and a current geographic location of the mobile device viaa communication network. The method further comprises determining, uponreceiving the current geographic location of the mobile device and thecurrent time of the mobile device, whether the current geographiclocation of the mobile device complies with the associated geographicconstraint for the message to be sent to the client application anddetermining whether the current time of the mobile device complies withthe associated time constraint for the message to be sent to the clientapplication and sending, when the current geographic location of themobile device is determined to comply with the associated geographicconstraint and when the current time of the mobile device is determinedto comply with the associated time constraint, the message for displayto the user at the mobile device via a message notification interface ofan operating system of the mobile device.

According to certain embodiments, systems are disclosed for optimizingdelivery of messages to mobile device users. One system includes amemory having processor-readable instructions stored therein and aprocessor configured to access the memory and execute theprocessor-readable instructions, which when executed by the processorconfigures the processor to perform a plurality of functions, includingfunctions to: receive a message to be sent to a client applicationexecutable at a mobile device of a user, along with an associated timeconstraint and an associated geographic constraint; determine a currenttime at the mobile device and a current geographic location of themobile device via a communication network; determine, upon receiving thecurrent geographic location of the mobile device and the current time ofthe mobile device, whether the current geographic location of the mobiledevice complies with the associated geographic constraint for themessage to be sent to the client application and determining whether thecurrent time of the mobile device complies with the associated timeconstraint for the message to be sent to the client application; andsend, when the current geographic location of the mobile device isdetermined to comply with the associated geographic constraint and whenthe current time of the mobile device is determined to comply with theassociated time constraint, the message for display to the user at themobile device via a message notification interface of an operatingsystem of the mobile device.

According to certain embodiments, a computer readable medium isdisclosed as storing instructions that, when executed by a computer,cause the computer to perform functions to: receive a message to be sentto a client application executable at a mobile device of a user, alongwith an associated time constraint and an associated geographicconstraint; determine a current time at the mobile device and a currentgeographic location of the mobile device via a communication network;determine, upon receiving the current geographic location of the mobiledevice and the current time of the mobile device, whether the currentgeographic location of the mobile device complies with the associatedgeographic constraint for the message to be sent to the clientapplication and determining whether the current time of the mobiledevice complies with the associated time constraint for the message tobe sent to the client application; and send, when the current geographiclocation of the mobile device is determined to comply with theassociated geographic constraint and when the current time of the mobiledevice is determined to comply with the associated time constraint, themessage for display to the user at the mobile device via a messagenotification interface of an operating system of the mobile device.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the scope of disclosed embodiments, as setforth by the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 is a view of a map showing multiple geo-fenced areas forproviding messages to mobile device users that are determined to complywith a geographic constraint;

FIG. 2 is a block diagram of an exemplary communication system suitablefor practicing an embodiment of the present disclosure;

FIG. 3 is a communication flow diagram of an exemplary process foroptimizing the timing of message notifications for a mobile device userbased on a current geographic location and a current time of the user'sdevice;

FIG. 4 is a communication flow diagram of an exemplary process foroptimizing the timing of message notifications for the mobile deviceuser of FIG. 3 based on a detected change in the current geographiclocation and a change in time of the user's device;

FIG. 5 is a process flow diagram of an exemplary method for optimizingthe timing of message notifications for a mobile device user based on acurrent geographic location and a current time of the user's device;

FIG. 6 is an exemplary table for associating different clientapplications with corresponding message queues; and

FIG. 7 is a block diagram of an exemplary computer system in whichembodiments of the present disclosure may be implemented.

DESCRIPTION OF THE EMBODIMENTS

The present disclosure is directed to overcoming one or more of theabove referenced issues. Specifically, the present disclosure isdirected to optimizing delivery of messages to mobile device users. Inorder to optimize the delivery, the message may include an indicationthat provides a time-based criterion and a geographic-based criterion,both of which are satisfied before releasing a queued message to anintended recipient. The optimizations are to ensure a better chance thata user of the mobile device receives the message when and where themessage is most needed and/or not to receive the message when it is notimportant or of less importance.

For example, one member of a household may notice that a particularhousehold staple is almost gone. The member of the household may want tonotify another member of the household to buy the particular householdstaple when the other member leaves work for the day by sending theother member a message. However, the member may not want to send theother member the message immediately because an immediate message mayinterrupt his or her work, and he or she may not remember the message bythe end of the day to buy the particular household staple (i.e., themessage is not relevant at the current time). Thus, the member may queuea message to the other member, by indicating that the message should besent after a predetermined time, such as after work at 5 pm, or during atime period, such as 5 pm to 8 pm, when the milk is needed. The membermay also want to indicate a geographic constraint on the message toensure that the message is received when other member leaves his or heroffice. The geographic constraint may be indicated as an area outside ofthe other member's office and/or an area within a few miles of a market,which ensures that the other member has left work and/or is near a placethat sells the particular household staple.

In another example, a user may want to queue a message that reminds himor her to silence his or her mobile phone when he or she enters a churchon Sunday. Accordingly, the user may queue a message to silence his orher cell phone with a geographic constraint of an area within a churchand a time constraint being any time on Sundays. The user may also wantto queue a message that reminds him or her to silence his or her mobilephone whenever he or she enters a movie theatre. Thus, the user mayqueue a message to silence his or her cell phone with a geographicconstraint of an area within a movie theatre and a time constraint beingalways.

In yet another example, a mother may want to queue a video message toher daughter when she gets home from school to let her know that she isout on an errand. Alternatively, the mother may want to queue a messageto her daughter 2 hours after she gets home to remind her to do herhomework. Thus, the mother may queue a message to her daughter with ageographic constraint of an area within the home and a time constraintof immediately and/or 2 hours later.

In another example of an embodiment, an application developer oraffiliated information service provider, e.g., a news agency or othermedia outlet, associated with a client application may provide a mobilemessaging service, to which the user may subscribe so as to authorizethe service provider to send (e.g., “push”) a message (e.g., breakingnews or other alerts) to the user's device via a mobile communicationnetwork when the user is within a geographic location where the messageis relevant (e.g., a storm warning near the user). The messages sent bya service provider associated with a client application executable atthe user's device may be displayed within a general notifications windowof a graphical user interface (GUI) of the device's operating system,even when the corresponding client application may not have beenlaunched by the user or be actively executing at the mobile device.

In the above examples, the geographic constraint may be a predeterminedgeographic area of any size and shape. The bounds of the geographic areamay be defined by, for example, a customized geo-fence or virtualperimeter surrounding or outside of a particular location or point ofinterest (POI) indicated by the message. Accordingly, the delivery ofthe message, which may be relevant to a POI located near the user'scurrent geographic location, may be triggered when the location of theuser's mobile device is determined to comply with the geographicconstraint. More specifically, the message may be relevant when the useris determined to be within the corresponding geo-fenced area (i.e., theuser has entered the geo-fence). Alternatively, the message may berelevant when the user is determined to be outside the correspondinggeo-fenced area (i.e., the user has exited the geo-fence).

The time constraint may indicate a predetermined time and/or apredetermined time period. The bounds of the time constraint may bedefined by, for example, after a predetermined time, before apredetermined time, within a predetermined time period, outside of apredetermined time period, or at all times.

Examples of time constraints may include predetermined time,predetermined days, predetermined days of the week or weekend, apredetermined month, and/or any known measure or period of time anddates. Accordingly, the delivery of a message, which may be relevant toa current time in which a user is currently located, may be triggeredwhen the time according to the user's mobile device is determined tocomply with the time constraint.

The messages are typically displayed within a designated portion of theclient application's own GUI as it executes at the user's device, e.g.,a pop-up, in a messaging application, or as a banner presented in abottom or top portion of the application's GUI (e.g., of a mobilebrowser) as it is displayed on a display screen of the user's device.The messages may be delivered to the user's device whenever the user'smobile device is turned on or the messages may be delivered only whenthe client application is actively executing at the device, e.g., afterthe user has manually launched the application for execution via a userinterface of the operating system at the mobile device.

When the messages are coming from a third-party content provider, suchas breaking news alerts relevant to the current user's location, theuser who has subscribed to messaging services offered by a serviceprovider associated with a client application executable at the user'sdevice may or may not have authorized the application service providerto send general messages (e.g., push notifications) related to topics ofinterest to the user's device. It may also be assumed for purposes ofthis example that the user has at least implicitly requested orauthorized third-party content providers (e.g., with whom theapplication service provider may have entered into a partnershipagreement) to deliver messages to the user's mobile device within adesignated portion of the application's GUI while the client applicationis actively executing at the user's device (e.g., pursuant to terms andconditions of use accepted by the user).

Reference will now be made in detail to the exemplary embodiments of thedisclosure, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 is a view of a map 100 showing multiple geo-fenced areas forproviding messages to mobile device users determined to be locatedwithin a geo-fenced area or outside of a geo-fenced area. As shown inFIG. 1, map 100 includes a geo-fenced area 102 and a geo-fenced area104. Each of geo-fenced areas 102 and 104 may be associated with amobile device. In an example, geo-fenced areas 102 and 104 may eachcorrespond to the location of a venue, public landmark, commercialbusiness (e.g., a restaurant, office, store, etc.), or other POI.Alternatively, the geo-fenced areas 102 and 104 may be inputted by oneor more users and represent a targeted geographic area of interest.Thus, the boundaries or dimensions of each of the geo-fenced areas 102and 104 may correspond to, for example, the shape and size of a buildingor other physical structure associated with the organization (e.g., arestaurant, office, store, or other place of business). Additionally, itshould be noted that geo-fenced areas 102 or 104 may be of any size andshape, as desired for a particular implementation. For example, the sizeand shape of each geo-fenced area may be based on a predetermined radiusaround a specified location, address, or POI.

Also, as shown in FIG. 1, map 100 indicates the geographic locations ofa user device 110 a, a user device 110 b, and a user device 110 c. Eachof user devices 110 a, 110 b, and 110 c may be implemented using, forexample, any type of mobile computing device including, but not limitedto, a laptop computer, tablet computer, mobile handset, smartphone,personal digital assistant (PDA), a dedicated portable GlobalPositioning System (GPS) navigation device, or similar type of mobiledevice. Further, each of user devices 110 a, 110 b, and 110 c may beequipped with a GPS receiver for registering GPS location data, e.g.,latitude and longitude coordinates, at a particular point or over aperiod of time. However, it should be noted that the physical orgeographic location of each of user devices 110 a, 110 b, and 110 c maybe determined or estimated using any one or a combination of variouswell-known techniques for deriving such geographic location information.Examples of such techniques include, but are not limited to, GPS, cellidentification (e.g., using Cell ID), cellular tower triangulation,multilateration, Wi-Fi, and any other network- or handset-basedtechnique for deriving or estimating the physical or geographic locationof a mobile device via a mobile communication network.

It should be noted that the physical or geographic location of each ofuser devices 110 a, 110 b, and 110 c may be used to determine orestimate a current time for each of the respective devices using any oneor a combination of various well-known techniques for deriving such timeinformation, such as a world clock.

Each of user devices 110 a, 110 b, and 110 c may be configured toreceive messages, send messages, and/or to execute one or more clientapplications. Such a client application executable at each of userdevices 110 a, 110 b, and 110 c may be associated with, for example, aninformation service provider or a messaging application. Further, eachof user devices 110 a, 110 b, and 110 c may be configured to receivemessages from the mobile user or other users, or messages related totopics of interest (e.g., breaking news alerts) for a user at eachdevice. As will be described in further detail below, such notificationsmay be sent to each of user devices 110 a, 110 b, and 110 c by a messageserver via a mobile communications network. The messages may be sent bythe message server as, for example, push notifications that areperiodically sent to each device. However, it should be noted that thetechniques disclosed herein are not limited to push notifications andthat these techniques may be applied with any type of messaging schemeor protocol used to deliver messages to user devices 110 a, 110 b, and110 c. For example, any of user devices 110 a, 110 b, or 110 c may beconfigured to request (or “pull”) pending messages from the messageserver via the mobile communication network.

Each of user devices 110 a, 110 b, and 110 c may be configured to sendmessages to each of the other user devices and or their own user device.For example, user device 110 a may send a message along with ageographic constraint and a time constraint to the user device 110 b,the user device 110 c, both the user devices 110 b and 110 c, their ownuser device 110 a, and/or all of the user devices 110 a, 110 b, and 110c.

As described above, the messages delivered to any of user devices 110 a,110 b, or 110 c for a particular client application, such as a messagingapplication, executable at the device may be displayed within, forexample, a general notifications window or similar type of user controlelement of a GUI provided by a mobile operating system at the device,particularly when the client application has not been opened or launchedby the user and thus, the client application is not actively executingat the user's device. The client application may be configured to alwaysbe opened or launched in the background of the user device. Further, theclient application may be configured to allow the user device to onlyreceive messages from only certain users. For example, the clientapplication on user device 110 a may be configured to only receivemessages, along with a geographic constraint and time constraint, fromusers or members within his or her social network and/or a contact ofthe user of the user device 110 a. In other words, the clientapplication on user device 110 a may be configured to “opt-in” toreceive messages from only particular social networks, contacts, users,and/or other services that send messages. Alternatively, the clientapplication on user device 110 a may be configured to “opt-out” fromreceiving messages from certain social networks, contacts, users, and/orother services that send messages.

As described above, each of user devices 110 a, 110 b, and 110 c may beconfigured to allow or disallow messages from certain social networks,contacts, users, and/or other services that send messages as specifiedin each of the respective user devices. For example, the user device 110a may be configured to only allow messages with associated geographicconstraints and time constraints from a contact list of user device 110a. In an embodiment, the contacts and/or users that are allowed to sendmessages to user device 110 a may be allowed to access the currentgeographic location of user device 110 a. If the contacts and/or usersof the user device 110 a are able to access the current geographiclocation of user device 110 a, they are able to set up geo-fences aroundor nearby user device 110 a. In this way, user device 110 a is morelikely to comply with the geographic constraints that are set up by thecontacts and/or users.

A GUI of a client application that is capable of sending messages, alongwith the geographic constraint and the time constraint, may include amap, such as map 100 as shown in FIG. 1, that allows a user of theclient application to set the predetermined geographic area associatedwith the message. For example, a user sending a message may set ageo-fence around a location on the map 100, such as the geo-fenced area104. Alternatively, the user may set a geo-fenced area around a user,such as the geo-fenced area 102 which is around user device 110 a. Thus,when user device 110 a a leaves the geo-fenced area, a message may besent to user device 110 a. In one embodiment, a user of the clientapplication may be able to see the current locations of various userdevices of users that are in his or her social network and/or contacts.Accordingly, the user is able to set geo-fenced areas around the currentlocations of the various user devices, and thus, be able to setgeographic constraints that are relevant to the various user devices.

As described above, the user of each device may have subscribed to aservice offered by an application service provider associated with aclient application executable at the user's device, which authorizes theapplication service provider to send relevant messages (e.g., as pushnotifications) to the user's device.

A message associated with geo-fenced area 102 may be provided to userdevice 110 a via a mobile communication network, when the geographiclocation of mobile device 110 a is determined to be within or outside ofgeo-fenced area 102. Similarly, a message associated with geo-fencedarea 104 may be provided to an appropriate client application executingat user device 110 c, when user device 110 c is determined to be withinor outside of geo-fenced area 104. However, as described above, in somecases, the messages may be provided to each of user devices 110 a and110 c only when the appropriate client application in this example isactively executing at each of user devices 110 a and 110 c.

In an example, a user of a client application executable at user device110 b may have subscribed to a messaging service provided by anapplication service provider associated with the client application inorder to receive push notifications related to topics or events ofinterest to the user. Such a messaging service may be hosted at amessage server associated with the client application or applicationservice provider. Additional details of such a message server will bedescribed in further detail below in reference to FIGS. 2-4. Examples ofdifferent push notifications that may be sent for the user at userdevice 110 b include, but are not limited to, messages inputted by theuser of the mobile device, messages from other users, news alertsrelated to topics or keywords previously specified by the user, systemor service-related message notifications, public safety advisories, andnotifications of comments or messages posted to an electronic messageboard by other users (e.g., members of a social networking groupassociated with the user of user device 110 b). The push notificationsmay be periodically sent by, for example, a messaging service of theapplication service provider to user device 110 b via a mobilecommunication network. The notifications received at user device 110 bmay be displayed in a general notifications window of a GUI provided bythe operating system of user device 110 b.

As indicated by map 100, the current geographic location of user device110 b in this example is outside of a designated geographic area, e.g.,corresponding to either of geo-fenced areas 102 or 104. Thus, upondetermining that user device 110 b does not currently comply with thegeographic constraint, the above-described messaging service provided bythe application service provider may add a new message, to be sent (orpushed) as a notification to user device 110 b, to a message queuemaintained by the message server. As will be described in further detailbelow, the determination of whether or not a particular geographiclocation complies with a geographic constraint may be made by a serverassociated with a service provider based on the current geographiclocation of user device 110 b. The current location of user device 110 bmay be forwarded to the server by an application server or messageserver associated with the application service provider

In some implementations, a message or message notification that may beadded to the message queue may be associated with a time constraint. Thetime constraint may be as described above or may be an expiration timethat may be used to determine the period of time that the message willbe kept in the queue before being delivered to user device 110 b,regardless of the device's current geographic location. The expirationtime associated with a queued message may be based on, for example, apredetermined time period that reflects a priority level assigned to theparticular message notification. For example, an important publicadvisory message or breaking news alert may be assigned a relativelyhigh priority level, and therefore, be associated with a relativelyshort expiration time. Thus, such high priority message notificationsmay be kept in the queue for a relatively short time period oralternatively, be sent immediately to user device 110 b, without beingadded to the message queue.

In the above example, user device 110 b may be configured toperiodically report its current geographic location and current time tothe application or message server as this location changes over a periodof time. As will be described in further detail below, upon receiving anindication of a new or updated current geographic location of userdevice 110 b, the message server may query the appropriate server todetermine whether the updated geographic location complies with thegeographic constraint. It should be noted that this determination may bemade by the application server or message server itself, e.g., based onstored information identifying the locations and boundaries of variousgeographic constraints. It should also be noted that the applicationserver or message server may communicate with multiple third-partyservers, which may be associated with different third-party providers,via an electronic communication network, as will be described in furtherdetail below.

If it is determined that the updated geographic location of user device110 b complies with the geographic constraint, e.g., within or outsideof geo-fenced area 102 or geo-fenced area 104, the message server maycheck the message queue for any previously queued messages. The messageserver may then request an updated time of user device 110 b, and thendetermine whether the updated time of the user device 110 b complieswith the time constraint. After confirming that both the geographicconstraint and time constraint are complied with, the server may thensend a message notification from the message queue to user device 110 b.In an alternative embodiment, the message server may check the timeconstraint before the geographic constraint, or the message server maycheck both the time constraint and geographic constraint concurrently.

FIG. 2 is a block diagram of an exemplary communication system 200 forpracticing embodiments of the present disclosure. As shown in FIG. 2,system 200 includes user devices 210 a, 210 b, and 210 c, an applicationserver 230 coupled to a database 235 and a message server 250 coupled toa database 255, all of which may be communicatively coupled via anelectronic communication network 220.

Network 220 may be any type of electronic network or combination ofnetworks used for communicating digital content and data between variouscomputing devices. Network 220 may include, for example, a local areanetwork, a medium area network, or a wide area network, such as theInternet. While only user devices 210 a, 210 b, and 210 c are shown inFIG. 2, system 200 may include any number of user devices. Similarly,while only application server 230 and message server 240 are shown inFIG. 2, it should be understood that system 200 may include additionalor fewer servers, as desired for a particular implementation. Further,while not shown in FIG. 2, network 220 may include various switches,routers, gateways, or other types of network devices used to facilitatecommunication between various computing devices via network 220.

In the example shown in FIG. 2, user device 210 a may be a laptop,notebook, netbook, or similar type of mobile computing device. Userdevice 210 b may be, for example, a tablet device or similar type ofmobile device having a touchscreen display. User device 210 c may be,for example, a mobile handset, smartphone, or personal digital assistant(“PDA”). However, it should be noted that each of user devices 210 a,210 b, and 210 c may be any type of mobile computing device configuredto send and receive different types of data including, but not limitedto, website data, multimedia content, electronic advertisements, and anyother type of digital information, over network 220. Examples of suchmobile computing devices include, but are not limited to, a laptopcomputer, a handheld computer, a personal digital assistant (PDA), acellular telephone, a network appliance, a camera, a smart phone, anenhanced general packet radio service (EGPRS) mobile phone, a mediaplayer, a navigation device, a portable game console, or any combinationof these computing devices or other types of mobile computing deviceshaving at least one processor, a local memory, a display, one or moreuser input devices, and a network communication interface. The userinput device(s) may include any type or combination of input/outputdevices, such as a display monitor, touchpad, touchscreen, microphone,camera, keyboard, and/or mouse.

Each of application server 230 and message server 240 may be any ofvarious types of servers including, but not limited to, a web server, aproxy server, a network server, or other type of server configured toexchange electronic information with other servers or computing devicesvia a communication network, e.g., network 220. Such a server may beimplemented using any general-purpose computer capable of serving datato other computing devices including, but not limited to, user devices210 a, 210 b, and 210 c or any other computing device (not shown) vianetwork 220. Such a server may include, for example and withoutlimitation, a processor and memory for executing and storingprocessor-readable instructions. The memory may include any type ofrandom access memory (RAM) or read-only memory (ROM) embodied in aphysical storage medium, such as magnetic storage including floppy disk,hard disk, or magnetic tape; semiconductor storage such as solid statedisk (SSD) or flash memory; optical disc storage; or magneto-opticaldisc storage. Software may include one or more applications and anoperating system. Hardware can include, but is not limited to, aprocessor, memory and graphical user interface display. The server mayalso be implemented using multiple processors and multiple shared orseparate memory devices within, for example, a clustered computingenvironment or server farm.

Also, as shown in FIG. 2, application server 230 and message server 240are communicatively coupled to databases 235 and 245, respectively. Eachof databases 235 and 245 may be a data store or memory accessible to thecorresponding server and may be implemented using any type of datastorage device or recording medium used to store various kinds of dataor content. Such data or content may include, for example and withoutlimitation, text or media content that may be later provided to each ofuser devices 210 a, 210 b, and 210 c via network 220.

In an example, each of user devices 210 a, 210 b, and 210 c may executea client application that communicates with application server 230and/or message server 240 via network 220. Further, each of user devices210 a, 210 b and 210 c may be configured to receive application contentthrough an interface provided by application server 230 via network 220.The content provided by application server 230 may be based on, forexample, user requests initiated via a GUI of the client applicationexecutable at each device. The GUI of the client application executableat each of user devices 210 a, 210 b, and 210 c may be configured topresent the content to a user at each device via a display of therespective user devices 210 a, 210 b, and 210 c. The GUI of the clientapplication may include, for example, various control elements enablingthe user to request various types of content, e.g., which may beassociated with a web site maintained by the application serviceprovider. Further, a portion of the GUI of the client application mayserve as a message view area used to display messages from another userand/or the user. Such a content view of the client application may be adedicated content area, e.g., displayed at the very top or bottomportion, of the application's GUI. Messages may be displayed within thecontent view of the client application when the client application isactively executing at user device 210 a, 210 b, or 210 c. Also, asdescribed above, the messages sent by an application provider fordisplay to the user via a general message notifications interface of theoperating system at user device 210 a, 210 b, or 210 c, even when theclient application is dormant or not actively executing at theparticular device.

Application server 230 may be configured to host a web service thatprovides users various types of functionality via a GUI of the clientapplication executable at each of user devices 210 a, 210 b and 210 c.Such functionality may include, for example and without limitation,providing digital content distributed by an application service providerassociated with the client application. The application service providermay be, for example, an online content provider, including thoseassociated with various search engines, e-mail programs, RSS feedproviders, magazines, e-zines, blogs, or any other online site orprogram that publishes or distributes online content related to, forexample, news or various topics of general public interest. As describedabove, a functionality provided by such an application service providermay include sending messages, e.g., push notifications, related totopics of interest, as specified by a user/subscriber of each userdevice and may include messages sent from other users. Also, asdescribed above, the messages sent to each device may be displayed forthe user via a message notifications interface of a mobile operatingsystem at each of user devices 210 a, 210 b, and 210 c if, for example,the client application has not been launched by the user or is notactively executing at the user's device.

Further, application server 230 and message server 240 may be configuredto communicate with one or more other third-party content servers (notshown) to retrieve content (e.g., electronic advertisements) via network220 to be displayed within a content view of a client applicationexecutable at each of user devices 210 a, 210 b, and 210 c. Further,application server 230 and message server 240 may each interact with oneanother, user devices 210 a, 210 b, or 210 c, or any other servers ornetwork devices (not shown) via network 220. Examples of such otherservers include, but are not limited to, DNS servers, ad servers, andcontent distribution servers.

Message server 240 in this example may be configured to control thesending of messages or push notifications to be sent via network 220 toeach of user devices 210 a, 210 b, and 210 c based on the currentgeographic location of each device relative to one or more geographicconstraints, e.g., geo-fenced areas 102 and 104, and/or time constraintsfor delivering the messages to a user at each device as described above.In an example, message server 240 may delay the sending of a messagewhen the current geographic location of the device is determined not tocomply with the geographic constraint and/or when the current time ofthe device is determined not to comply with the time constraint. As willbe described in further detail below, message server 240 may add themessage to a message queue for the client application. Message server240 may be configured to send the message from the message queue to userdevice 210 a, 210 b, or 210 c via network 220, upon receiving anindication of an updated current geographic location of the device andupdated current time of the device and determining that the new orupdated location complies with the geographic constraint and/ordetermining that the updated time complies with the time constraint.

In an example, message server 240 may determine whether or not thecurrent geographic location of user device 210 a, 210 b, or 210 ccomplies with the geographic constraint, as described above and as willbe described in further detail below. Message server 240 may beconfigured to receive a request including the current geographiclocation of user device 210 a, 210 b, or 210 c and send an appropriateresponse to user device 210 a, 210 b, or 210 c after determining whetherthe received geographic location complies with the geographicconstraint. The geographic constraint may be one of a plurality ofdifferent areas corresponding to various predetermined geographic areasfor providing the message to mobile device users when each user's mobiledevice is determined to comply with the geographic constraint. Asdescribed above, the message delivered to a user's device may berelevant to a particular location or POI associated with the geographicarea. Further, the delivery of such message may be triggered when theuser's mobile device is detected within the boundary of a geo-fencecorresponding to the geographic area or is detected outside of theboundary of a geo-fence corresponding to the geographic area.

In another example, message server 240 may determine whether or not thecurrent time of user device 210 a, 210 b, or 210 c complies with thetime constraint, as described above and as will be described in furtherdetail below. Message server 240 may be configured to receive a requestincluding the current time of user device 210 a, 210 b, or 210 c andsend an appropriate response to user device 210 a, 210 b, or 210 c afterdetermining whether the received time complies with the time constraint.The time constraint may be one of a plurality of different timingscorresponding to various predetermined times or time periods forproviding the message to mobile device users when each user's mobiledevice is determined to comply with the time constraint. As describedabove, the message delivered to a user's device may be relevant to aparticular time or period of time. Further, the delivery of such messagemay be triggered when the user's mobile device is detected within theboundary of a time constraint or is detected outside of the boundary ofa time constraint. As described above, the bounds of the time constraintmay be defined by, for example, after a predetermined time, before apredetermined time, within a predetermined time period, outside of apredetermined time period, or at all times.

In an alternative embodiment, the message server 240 may check the timeconstraint before the geographic constraint, or the message server maycheck both the time constraint and geographic constraint concurrently.

In some implementations, message server 240 may be implemented as aback-end component that interfaces with only application server 230.Thus, it should be noted that for some implementations, message server240 may be configured to act only with application server 230, withoutany direct communication with any of user devices 210 a, 210 b, or 210c, in order to facilitate the message notification timing functionalitydescribed herein. Accordingly, application server 230 and message server240 may be configured to exchange information in the form of messages,requests, or responses that are passed between the servers. Thecommunication between application server 230 and message server 240 maybe over network 220 or a virtual private network accessible to eachserver. In an example, messages added to the message queue may be routedfrom message server 240 to application server 230, when it is determinedthat user device 210 a, 210 b, or 210 c complies with the geographicconstraint. Application server 230 may then send the routed message touser device 210 a, 210 b, or 210 c via network 220. However, it shouldbe noted that the functions performed by application server 230 andmessage server 240 or a combination thereof, as described herein, may beimplemented using a single server. Additional features andcharacteristics of the communication between user devices 210 a, 210 b,and 210 c, application server 230 and message server 240 will bedescribed in further detail below with respect to FIGS. 3 and 4.

FIG. 3 is a communication flow diagram of an exemplary process 300 foroptimizing the timing of message notifications for a mobile device userbased on a current geographic location of the user's device relative toa geographic constraint and based on a current time at or of the user'sdevice relative to a time constraint, as described above. The exampleshown in FIG. 3 illustrates the communication flow between a user device310, an application server 330, and a message server 340. For purposesof discussion, process 300 will be described using map 100 of FIG. 1 andsystem 200 of FIG. 2, as described above, but process 300 is notintended to be limited thereto. Thus, user device 310 may be implementedusing, for example, any of user devices 210 a, 210 b, or 210 c of FIG.2, as described above. Similarly, application server 330 and messageserver 340 may be implemented using, for example, application server 230and message server 240, respectively, as described above.

As shown in FIG. 3, application server 330 may send a new messagenotification request for a client application executable at user device310 to message server 340 via a communication network, e.g., network 220of FIG. 2, as described above (step 301). Message server 340 may in turnrequest a current geographic location of user device 310 and a currenttime at or of user device 310 (step 302). Alternatively, the currenttime can be determined by the current location of the user device 310and a world clock. The request may be sent by message server 340directly to user device 310, as shown in FIG. 3, or alternatively,message server 340 may send the request to application server 330, whichmay then request the geographic location information and the timeinformation from user device 310, if necessary. In some implementations,application server 330 may respond to the request from message server340 by sending a last known or previously determined or estimatedgeographic location and/or time of user device 310, e.g., which may bestored in a memory or data store (e.g., database 235 of FIG. 2, asdescribed above) coupled to application server 330. Accordingly, userdevice 310 may send the requested location data (or current geographiclocation information) and the time information to message server 340(step 303), or to whichever server (e.g., application server 330) mayhave requested the information from user device 310.

Message server 340 may determine whether or not the current geographiclocation of user device 310 complies with the geographic constraint andwhether or not the current time of user device 310 complies with thetime constraint, as described above (step 304). The geographicconstraint may correspond to, for example, a predetermined geographicarea bounded by a virtual perimeter of a geo-fence, as described above,and the time constraint may correspond to the above described timeboundaries. For example, the geographic constraint may be one of manyareas corresponding to different geo-fenced areas, e.g., geo-fencedareas 102 and 104 of FIG. 1, as described above. The geographicconstraint may be, for example, the detecting of leaving a boundary,e.g., crossing a boundary in a direction of inside a geo-fenced area tooutside the geo-fenced area or crossing a boundary in a direction ofoutside a geo-fenced area to inside the geo-fenced area. If the currentgeographic location of user device 310 is determined to comply with thegeographic constraint and/or the current time of user device 310 isdetermined to comply with the time constraint, message server 340 maysend the message notification to user device 310 for display to the userat user device 310 via a general notifications interface of theoperating system of user device 310, as described previously (step 305).Alternatively, if the device's location is determined not to comply withthe geographic constraint and/or the current time is determined not tocomply with the time constraint, the message may be added to a messagequeue to be sent at a later time, as described above.

FIG. 4 is a communication flow diagram of an exemplary process 400 foroptimizing the timing of message notifications for the user of mobiledevice 310 of FIG. 3, as described above, based on a detected change inthe current geographic location of the user's device relative to thegeographic constraint and/or based on a change in the current time ofthe user's device relative to the time constraint. As shown in FIG. 4,the detected change in location may be based on, for example, an updatedcurrent geographic location sent by user device 310 or an operatingsystem thereof to application server 330 via a network, e.g., network220 of FIG. 2, as described above. The change in time may be based on,for example, an updated time sent by user device 310, an operatingsystem thereof to application server 330, and/or by determining thecurrent time by extrapolating the time from the geographic informationand a known time via a network, e.g., network 220 of FIG. 2, asdescribed above (step 401).

Application server 330 may then notify message server 340 of the updatedgeographic location information and updated time information receivedfrom user device 310 (step 402). In response to the notification fromapplication server 330, message server 340 may determine whether theupdated current location and updated time of user device 310 complieswith the geographic constraint and the time constraint, respectively(step 403). If the determination indicates that the updated locationcomplies with the geographic constraint and the updated time informationcomplies with the time constraint, message server 340 may check amessage queue associated with the particular client applicationexecutable at user device 310 to determine if there are any pendingmessage notifications within the queue that need to be sent to userdevice 310, e.g., as added previously by message server 340 (at step 305of process 300 of FIG. 3, as described above). Message server 340 maysend the message to user device 310 via a communication network, e.g.,network 220 of FIG. 2 (step 404), only if a message is found within themessage queue or do nothing otherwise.

FIG. 5 is a process flow diagram of an exemplary method 500 foroptimizing the timing of message notifications for a mobile device userbased on a current geographic location of the user's device relative toa geographic constraint and based on a current time of the user's devicerelative to a time constraint. For purposes of discussion, method 500will be described using system 200 of FIG. 2 and the components ofprocesses 300 and 400 of FIGS. 3 and 4 (including application server 330and message server 340), as described above, but method 500 is notintended to be limited thereto. As shown in FIG. 5, method 500 includessteps 502, 504, 506, 508, 510, 512, 514, and 516. However, it should benoted that method 500 may include more or fewer steps as desired for aparticular implementation. In an example, one or more of theabove-listed steps of method 500 may be executed by message server 240of FIG. 2 or message server 340 of FIGS. 3 and 4, as described above.However, method 500 is not intended to be limited thereto, and the stepsof method 500 may be performed by any server (e.g., application server230 of FIG. 2 or application server 330 of FIGS. 3 and 4) or other typeof computing device having at least one processor, a memory, and anetwork communication interface for sending and receiving informationfrom one or more user devices.

Method 500 begins in step 502, which includes receiving a message for aclient application executable at a user's mobile device (e.g., userdevice 210 of FIG. 2 or user device 310 of FIGS. 3 and 4, as describedabove). The message may include a geographic constraint and/or a timeconstraint, as described above.

In step 504, a current geographic location of the mobile device and acurrent time of the mobile device are requested and received from themobile device.

Steps 506 and 508 may include, for example, determining whether acurrent geographic location of the mobile device complies with ageographic constraint and whether a current time of the mobile devicecomplies with a time constraint. If it is determined in step 508 thatthe current geographic location of the mobile device complies with thegeographic constraint and the current time of the mobile device complieswith the time constraint, method 500 may proceed to step 510, whichincludes sending a message from a message queue to the mobile device,and ends.

It should be noted that step 510 may also include first checking themessage queue to determine whether or not it includes any pendingmessages to be sent to the mobile device for the particular clientapplication. The message queue in this example may be associated withthe particular client application. In an example, an association betweena queue of messages and a unique identifier associated with the clientapplication may be maintained, e.g., by message server 240 of FIG. 2 ormessage server 340 of FIGS. 3 and 4, as described above. FIG. 6 shows anexemplary table 600 that may be used for associating different clientapplications, represented by corresponding client applicationidentifiers 602 and their respective message queues 604. As shown intable 600, each message that is added to a message queue associated witha client application may include a time constraint used to determine atime that the message may be kept in the queue before being sent to theuser's device or deleting the message from the queue, regardless of itscurrent geographic location, as described above. Table 600 may be storedwithin a database (e.g., database 245 of FIG. 2) coupled to the serverin this example.

However, if it is determined in step 508 that the current geographiclocation of the mobile device does not comply with the geographicconstraint or the current time of the mobile device does not comply withthe time constraint, method 500 may proceed to step 512. In step 512,the message with the geographic constraint and the time constraint isadded to the appropriate message queue. Method 500 then proceeds to step514, which includes waiting for a predetermined event to be triggered orthe expiration time of the message to elapse. An example of such apredetermined event includes, but is not limited to, receiving anotification of an updated or detected change in current geographiclocation and/or current time for the mobile device.

The method 500 proceeds to step 516, which may include receiving anotification of an updated geographic location and/or time of the mobiledevice, e.g., a type of predetermined event trigger described above withrespect to step 514, and proceeds to step 506. In an example, theaforementioned server may store an association between each of variousclient applications executable at the user's device and one or moregeographic constraints and/or time constraints corresponding to eachclient application. Such information may be stored within a table, forexample, table 600 of FIG. 6, as described above, along with the messagequeue and expiration time information.

FIG. 7 provides a high-level functional block diagram illustrating anexemplary general purpose computer 700. Computer 700 may be used toimplement, for example, any of application server 230 and message server240 of FIG. 2 in addition to application server 330 and message server340 of FIGS. 3 and 4, as described above. It is believed that thoseskilled in the art are familiar with the structure, programming andgeneral operation of such computer equipment and as a result thedrawings should be self-explanatory.

In an example, computer 700 may represent a computer hardware platformfor a server or the like. Accordingly, computer 700 may include, forexample, a data communication interface for packet data communication760. The platform may also include a central processing unit (CPU) 720,in the form of one or more processors, for executing programinstructions. The platform typically includes an internal communicationbus 710, program storage and data storage for various data files to beprocessed and/or communicated by the platform such as ROM 730 and RAM740, although the computer 700 often receives programming and data vianetwork communications 770. The hardware elements, operating systems andprogramming languages of such equipment are conventional in nature, andit is presumed that those skilled in the art are adequately familiartherewith. Computer 700 also may include input and output ports 750 toconnect with input and output devices such as keyboards, mice,touchscreens, monitors, displays, etc. Of course, the various serverfunctions may be implemented in a distributed fashion on a number ofsimilar platforms, to distribute the processing load. Alternatively, theservers may be implemented by appropriate programming of one computerhardware platform.

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the mobilecommunication network into the computer platform of a server and/or froma server to the mobile device. Thus, another type of media that may bearthe software elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

The many features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended by the appended claimsto cover all such features and advantages of the disclosure which fallwithin the true spirit and scope of the disclosure. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the disclosure to theexact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the disclosure.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

1-20. (canceled)
 21. A computer-implemented method for optimizingdelivery of messages to mobile device users, the method comprising:receiving a message to be sent to a client application executable at amobile device of a user, along with an associated time constraint and anassociated geographic constraint; determining a current time at themobile device and a current geographic location of the mobile device viaa communication network; determining, upon receiving the currentgeographic location of the mobile device and the current time of themobile device, whether the current geographic location of the mobiledevice complies with the associated geographic constraint for themessage to be sent to the client application and determining whether thecurrent time of the mobile device complies with the associated timeconstraint for the message to be sent to the client application; andsending, when the current geographic location of the mobile device isdetermined to comply with the associated geographic constraint and whenthe current time of the mobile device is determined to comply with theassociated time constraint, the message for display to the user at themobile device via a message notification interface of an operatingsystem of the mobile device, wherein the associated time constraint isbased on an expiration time associated with the message that is added toa message queue, the expiration time being based on a priority levelassigned to the message by an application service provider associatedwith the client application, such that the message is removed from themessage queue when the expiration time elapses, and such that themessage is sent to the mobile device for display to the user withoutbeing added to the message queue when the message is assigned a highpriority level.
 22. The method of claim 21, further comprising: adding,when at least one of the associated geographic constraint and theassociated time constraint has been determined not to be complied with,the message to the message queue, wherein the added message is to besent from the message queue for display to the user at the mobile devicewhen a detected change in the current geographic location of the mobiledevice is determined to comply with the associated geographic constraintand the current time of the mobile device is determined to comply withthe associated time constraint.
 23. The method of claim 21, wherein themessage, along with the associated time constraint and the associatedgeographic constraint, to be sent to the client application is from atleast one of a member of a social network of the user of the mobiledevice and a contact of the user of the mobile device.
 24. The method ofclaim 22, further comprising: determining, upon receiving an indicationof an updated current time of the mobile device, whether or not theupdated current time of the mobile device complies with the associatedtime constraint; determining, upon receiving an indication of an updatedcurrent geographic location of the mobile device, whether or not theupdated current geographic location of the mobile device complies withthe associated geographic constraint; and providing the message from themessage queue to be displayed for the user within the messagenotification view when the updated current time of the mobile device isdetermined to comply with the associated time constraint and when theupdated geographic location of the mobile device is determined to complywith the associated geographic constraint.
 25. The method of claim 21,wherein the message is sent from the message queue for display to theuser at the mobile device when the current geographic location of themobile device is later determined to comply with the associatedgeographic constraint before the expiration time has elapsed or once theexpiration time for the message is determined to have elapsed.
 26. Themethod of claim 21, wherein the associated time constraint is at leastone of a time being within a predetermined time period, the time beingoutside of the predetermined time period, the time being after apredetermined time, and the time being after a predetermined time. 27.The method of claim 21, wherein the associated geographic constraint isat least one of a geographic location inside of a predeterminedgeographic area, a geographic location outside of a predeterminedgeographic area, an entering of a predetermined geographic area, and anexiting of a predetermined geographic area.
 28. A system for timingmessage notifications to optimize delivery of messages to mobile deviceusers, the system comprising: a memory having processor-readableinstructions stored therein; and a processor configured to access thememory and execute the processor-readable instructions, which whenexecuted by the processor configures the processor to perform aplurality of functions, including functions to: receive a message to besent to a client application executable at a mobile device of a user,along with an associated time constraint and an associated geographicconstraint; determine a current time at the mobile device and a currentgeographic location of the mobile device via a communication network;determine, upon receiving the current geographic location of the mobiledevice and the current time of the mobile device, whether the currentgeographic location of the mobile device complies with the associatedgeographic constraint for the message to be sent to the clientapplication and determining whether the current time of the mobiledevice complies with the associated time constraint for the message tobe sent to the client application; and send, when the current geographiclocation of the mobile device is determined to comply with theassociated geographic constraint and when the current time of the mobiledevice is determined to comply with the associated time constraint, themessage for display to the user at the mobile device via a messagenotification interface of an operating system of the mobile device,wherein the associated time constraint is based on an expiration timeassociated with the message that is added to a message queue, theexpiration time being based on a priority level assigned to the messageby an application service provider associated with the clientapplication, such that the message is removed from the message queuewhen the expiration time elapses, and such that the message is sent tothe mobile device for display to the user without being added to themessage queue when the message is assigned a high priority level. 29.The system of claim 28, wherein the processor is further configured toperform functions to: add, when at least one of the associatedgeographic constraint and the associated time constraint has beendetermined not to be complied with, the message to the message queue,wherein the added message is to be sent from the message queue fordisplay to the user at the mobile device when a detected change in thecurrent geographic location of the mobile device is determined to complywith the associated geographic constraint and the current time of themobile device is determined to comply with associated the timeconstraint.
 30. The system of claim 29, wherein the processor is furtherconfigured to perform functions to: determine, upon receiving anindication of an updated current time of the mobile device, whether ornot the updated current time of the mobile device complies with theassociated time constraint; determine, upon receiving an indication ofan updated current geographic location of the mobile device, whether ornot the updated current geographic location of the mobile devicecomplies with the associated geographic constraint; and provide themessage from the message queue to be displayed for the user within themessage notification view when the updated current time of the mobiledevice is determined to comply with the associated time constraint andwhen the updated geographic location of the mobile device is determinedto comply with the associated geographic constraint.
 31. The system ofclaim 28, wherein the message is sent from the message queue for displayto the user at the mobile device when the current geographic location ofthe mobile device is later determined to comply with the associatedgeographic constraint before the expiration time has elapsed or once theexpiration time for the message is determined to have elapsed.
 32. Thesystem of claim 28, wherein the associated time constraint is at leastone of a time being within a predetermined time period, the time beingoutside of the predetermined time period, the time being after apredetermined time, and the time being after a predetermined time. 33.The system of claim 28, wherein the associated geographic constraint isat least one of a geographic location inside of a predeterminedgeographic area; a geographic location outside of a predeterminedgeographic area, an entering of a predetermined geographic area, and anexiting of a predetermined geographic area.
 34. A non-transitorycomputer readable medium storing instructions that, when executed by acomputer, cause the computer to perform functions to: receive a messageto be sent to a client application executable at a mobile device of auser, along with an associated time constraint and an associatedgeographic constraint; determine a current time at the mobile device anda current geographic location of the mobile device via a communicationnetwork; determine, upon receiving the current geographic location ofthe mobile device and the current time of the mobile device, whether thecurrent geographic location of the mobile device complies with theassociated geographic constraint for the message to be sent to theclient application and determining whether the current time of themobile device complies with the associated time constraint for themessage to be sent to the client application; and send, when the currentgeographic location of the mobile device is determined to comply withthe associated geographic constraint and when the current time of themobile device is determined to comply with the associated timeconstraint, the message for display to the user at the mobile device viaa message notification interface of an operating system of the mobiledevice, wherein the associated time constraint is based on an expirationtime associated with the message that is added to a message queue, theexpiration time being based on a priority level assigned to the messageby an application service provider associated with the clientapplication, such that the message is removed from the message queuewhen the expiration time elapses, and such that the message is sent tothe mobile device for display to the user without being added to themessage queue when the message is assigned a high priority level. 35.The non-transitory computer readable medium of claim 34, wherein thecomputer is further configured to perform functions to: add, when atleast one of the associated geographic constraint and the associatedtime constraint has been determined not to be complied with, the messageto the message queue, wherein the added message is to be sent from themessage queue for display to the user at the mobile device when adetected change in the current geographic location of the mobile deviceis determined to comply with the associated geographic constraint andthe current time of the mobile device is determined to comply with theassociated time constraint.
 36. The non-transitory computer readablemedium of claim 35, wherein the computer is further configured toperform functions to: determine, upon receiving an indication of anupdated current time of the mobile device, whether or not the updatedcurrent time of the mobile device complies with the associated timeconstraint; determine, upon receiving an indication of an updatedcurrent geographic location of the mobile device, whether or not theupdated current geographic location of the mobile device complies withthe associated geographic constraint; and provide the message from themessage queue to be displayed for the user within the messagenotification view when the updated current time of the mobile device isdetermined to comply with the associated time constraint and when theupdated geographic location of the mobile device is determined to complywith the associated geographic constraint.
 37. The non-transitorycomputer readable medium of claim 34, wherein the associated timeconstraint is at least one of a time being within a predetermined timeperiod, the time being outside of the predetermined time period, thetime being after a predetermined time, and the time being after apredetermined time.
 38. The non-transitory computer readable medium ofclaim 34, wherein the associated geographic constraint is at least oneof a geographic location inside of a predetermined geographic area, ageographic location outside of a predetermined geographic area, anentering of a predetermined geographic area, and an exiting of apredetermined geographic area.
 39. The non-transitory computer readablemedium of claim 34, wherein the message, along with the associated timeconstraint and the associated geographic constraint, to be sent to theclient application is from at least one of a member of a social networkof the user of the mobile device and a contact of the user of the mobiledevice.
 40. The non-transitory computer readable medium of claim 34,wherein the message is sent from the message queue for display to theuser at the mobile device when the current geographic location of themobile device is later determined to comply with the associatedgeographic constraint before the expiration time has elapsed or once theexpiration time for the message is determined to have elapsed.